Clear gRPC Monitor request only after monitor successfully closes #1771
+21
−16
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please check if the PR fulfills these requirements
before creating one)
our contributing guidelines
UPGRADING.md
has been updated with a migration guide (for breaking changes)What kind of change does this PR introduce?
This is a countermeasure for kernel/firwmare bugs: resources may take a few milliseconds to actually get freed for real after killing the process, or even after a regular closing.This delay makes the caller more resilient to this kind of issues.The gRPC
Monitor
request is closed only after the monitor is successfully closed.What is the current behavior?
gRPC callers of
Monitor
will get the streaming request close as soon as the CLI asks the monitor to "close" (but without waiting for the monitor to actually close).What is the new behavior?
Now the streaming request is closed after the monitor process executes the "close" operation
Does this PR introduce a breaking change, and is titled accordingly?
No